From agility to productivity An analysis of agile method fragments

Organisations want to influence the productivity of their development teams. There are a variety of methods available for teams to use for its development purposes, this study focuses on the agile development methodology. Currently there is no knowledge to which extent elements of agile development influence productivity. This research project identified influences on productivity by means of analysing process changes within development teams (i.e. addition, change, or deletion of a method element). Productivity is the main subject for this research project and is operationalizes and scoped by a triangular model describing three types of metrics: technical (LOC), functionality (user stories, tasks, bug fixes), and quality (post release defects). The aforementioned three metrics were measured at each method fragment which was analysed. Twenty five method fragments were identified and found eligible for productivity analyses. Ten development teams of the case company were interviewed in order to identify process changes during its agile usage. Twenty eight process changes were identified at these teams. A selection of teams was necessary since the productivity analysis phase and quantitative backlog of the teams was substantial in terms of size. This selection was established by means of five criteria assessments. A detailed quantitative analysis method was used, of which for instance the complexity of the functionality measurements was a challenge. Thirteen method fragments in total were analysed on its influence on productivity. From these thirteen method fragment, eight were found to have an effect on productivity. Five method fragments had an effect specifically on productivity namely the scrum board, the product backlog, the burn down chart, the demo, and sprints. Three method fragments had an effect specifically on quality, being pair programming, the sprint backlog, and self-contained teams. The effects on productivity were of varying strengths. An interpretation of the results is added to support organisations into understanding exactly why certain method fragments did have an effect while other method fragments did not. Teams experienced process changes in varying ways. Most teams indicated that introduced method fragments needed time and refinement to be integrated in an efficient manner within the development process. The results and corresponding effects are validated by means of expert sessions. This research made a contribution to the field of productivity, method engineering, and agile development by identifying which method fragments of agile development methods influenced productivity and to which degree it had an effect. It is the first research project which measured productivity on a method fragment level.